docs(ospo): community health rollout v2 — README, agents.md, health files#4873
Open
dj4oC wants to merge 2 commits into
Open
docs(ospo): community health rollout v2 — README, agents.md, health files#4873dj4oC wants to merge 2 commits into
dj4oC wants to merge 2 commits into
Conversation
|
|
dj4oC
force-pushed
the
ospo/community-health-v2
branch
from
24dd905 to
a9f9f27
Compare
…iles Introduced by the Kiteworks Open Source Program Office (OSPO) on May 5, 2026. Changes: - README.md: rewritten with OSPO v2 template — license-specific migration guidance, Community & Support section, Contributing workflow, Security section pointing to security.owncloud.com + YesWeHack bug bounty - agents.md: AI agent context file with architecture, build commands, and OSPO Policy Constraints (GitHub Actions, Dependabot, Git Workflow) - CODE_OF_CONDUCT.md: redirect to https://owncloud.com/contribute/code-of-conduct/ - CONTRIBUTING.md: redirect to https://owncloud.com/contribute/ - SECURITY.md: redirect to https://security.owncloud.com + YesWeHack - SUPPORT.md: redirect to https://owncloud.com/contact-us/ + channels OSPO: https://kiteworks.com/opensource Signed-off-by: David Walter <david.walter@kiteworks.com>
jesmrec
force-pushed
the
ospo/community-health-v2
branch
from
73eb061 to
73aca4c
Compare
DeepDiver1975
requested review from
jesmrec and
joragua
and removed request for
DeepDiver1975
joragua
requested changes
Jun 3, 2026
| - All code contributions must be compatible with the **GPL-2.0** license | ||
| - Do not introduce new **copyleft-licensed dependencies** (GPL, AGPL, LGPL, MPL) without explicit discussion in an issue first. This is especially important for repos migrating to Apache 2.0. | ||
| - Do not introduce new dependencies without discussion in an issue first | ||
| - Minimum SDK version is 24 (Android 7.0), target SDK is 35 |
Contributor
There was a problem hiding this comment.
Target SDK is 36 and the minimum SKD version will be updated in the next release (4.9)
Contributor
There was a problem hiding this comment.
IMO, we should change the target SDK when the release is out, not before.
| - **Rebase policy**: Always rebase; never create merge commits. Use `git pull --rebase` and `git rebase` before pushing. | ||
| - **Signed commits**: All commits **must** be PGP/GPG signed (`git commit -S -s`). | ||
| - **DCO sign-off**: Every commit needs a `Signed-off-by` line (`git commit -s`). | ||
| - **Conventional Commits & Squash Merge**: Use the [Conventional Commits](https://www.conventionalcommits.org/) format where the repository enforces it. Many repos use squash merge, where the PR title becomes the commit message on the default branch — apply Conventional Commits format to PR titles as well. A reusable GitHub Actions workflow enforces this. |
Contributor
There was a problem hiding this comment.
In the Android repo, we are not using conventional commits for PR titles and squash merge. Should we adapt it? 🤔
Member
There was a problem hiding this comment.
I'd welcome this - we want to have a consistent process on all repos - thank you
Contributor
There was a problem hiding this comment.
We'll adapt the PR titles to ConCom and so on, not a problem.
Honestly, i'm not a fan of squashing, it's something that should not make difference. Will think about it.
Comment on lines
-7
to
-8
| | <img src="docs_resources/filelist_device.png"> | <img src="docs_resources/photos_device.png"> | <img src="docs_resources/share_device.png"> | <img src="docs_resources/spaces_device.png"> | | ||
| | ---------------------------------------------- | -------------------------------------------- | ------------------------------------------- | ------------------------------------------- | |
Contributor
There was a problem hiding this comment.
Images removed from README. Is it OK?
Contributor
There was a problem hiding this comment.
I'd recover them as app screenshots
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR is part of the Kiteworks OSPO community health rollout (kiteworks.com/opensource), applied to all ~110 public ownCloud repositories starting May 5, 2026.
Test plan
🤖 Generated with Claude Code as part of the ownCloud OSPO rollout.
Kiteworks OSPO: https://kiteworks.com/opensource